What

Stacked on #1602 (which is stacked on #1601). Migrates the template build-context uploads (streaming the build archive to S3 presigned URLs in build_api.upload_file) onto pyqwest via its httpx-compatible transport adapter.

Originally deferred from #1601 because S3 presigned URLs reject chunked transfer encoding and Content-Length framing through reqwest was unverified. Verified at the wire level (raw-socket capture server): httpx's Content-Length — derived from the spooled archive (sync) or set explicitly on the async-iterator body (async) — is forwarded by the adapter and reqwest keeps Content-Length framing for streamed bodies, no chunked fallback.

How

• e2b/template_sync/build_api.py / template_async/build_api.py: upload_file uses a one-off pyqwest transport (ApiPyqwestTransport from feat(python-sdk): move the REST API client onto pyqwest's httpx transport adapter #1601) instead of the generated client's httpx transport.
• verify_ssl=False on the generated client is no longer honored for uploads (pyqwest has no insecure-TLS option), and http2=False is gone (S3 negotiates HTTP/1.1 via ALPN anyway).
• The 1-hour upload timeout now bounds the entire upload rather than each socket write — arguably the intended meaning for that endpoint.

Testing

• tests/{sync,async}/*/test_upload_file.py (the [JS SDK] uploadFile uses chunked transfer encoding, causing 501 NotImplemented on S3 presigned PUT URLs #1243 regression tests — Content-Length present and equal to the body, no chunked encoding) pass through pyqwest; the capture handlers now compare header names case-insensitively since hyper lowercases them where httpcore title-cased.
• Lint (ruff), typecheck (ty), unit suite: green.

Usage example

No API changes — template builds upload their context exactly as before:

from e2b import Template

template = Template().from_image("ubuntu:22.04").copy("data/", "/data")
Template.build(template, alias="my-template")   # archive upload now goes through pyqwest

🤖 Generated with Claude Code